Virtual channel remapping

ABSTRACT

Virtual channel enabled networking devices may map frames to specific virtual channels based upon frame characteristics (e.g. destination address, class of service). Devices and methods that provide a remapping of virtual channels are disclosed. In one embodiment, a network having virtual channel remapping may include: a first set of one or more switches that each support a first number of virtual channels, and a second set of one or more switches that each support a second number of virtual channels different from the first number of virtual channels. At least one switch from the second set is coupled to at least one switch from the first set and is configured to establish a correspondence (“map”) between the virtual channels supported by the first set and the virtual channels supported by the second set.

BACKGROUND

Computer networks may facilitate communication by establishing linksbetween nodes (e.g. computer, server, and stand-alone peripheral) of anetwork. These links may be physical or logical paths from a sender of apiece of information to its receiver. Each node of a network dependsupon these links to communicate with other nodes. The information may becommunicated in the form of data blocks, commonly referred to as frames.

Due to the growing number of nodes in networks, it is often impracticalto directly connect every pair of sender-receiver nodes with a directlink. Consequently, many networks include switches for routing framesthrough shared intermediate links. Each switch may include multipleports through which frames enter and exit the switch on network links.The switch is responsible for routing frames onto links which transportthe frames closer to their destination. Each switch may besimultaneously routing frames from multiple nodes through multiple linksof the network.

Each link has a limit to the rate at which frames may be transported.Since competing frames must share links, each switch includes a queuingscheme for frames directed to a given link. Unless the queuing scheme iscarefully designed, it is possible for queues to overflow or for framesto be “blocked” in a queue indefinitely while the link is tied up. Ascan be appreciated, blocking and other conflict mechanisms may preventdata from flowing expeditiously through the network. The efficiency ofthe network may be measured in terms of the maximum data rate, or“throughput”, and in terms of latency. Latency is the time it takes fordata to travel from its source to its destination in the network.

To combat blocking and other degradations of network efficiency, virtualchannels may be used. Virtual channels are independent logical linksassociated with a physical link.

FIG. 1 shows a simplified example of how the efficiency of a networkwithout virtual channels may be decreased by blocking In FIG. 1, twoswitches 102 and 104 are coupled by a link 106. Switch 102 includes aqueue 108 for frames directed over link 106, and switch 104 includes abuffer 110 for frames received over link 106. Frames traveling from portA of switch 102 to Port E of switch 104 are labeled “E”, while framestraveling from port B of switch 102 to port F of switch 104 are labeled“F”. Frames of both types travel across the shared link 106.

Traffic congestion may prevent a switch (e.g., switch 104) fromexpeditiously sending a frame (e.g., an E frame) on to the next link.When this happens, buffer 110 may accumulate frames while the switch iswaiting to forward the frame at the head of the buffer 110. If thebuffer 110 fills, switch 104 may notify switch 102 to stop sendingframes. In other words, the link becomes “blocked”, not only for theframes targeted to a congested area (e.g., the E frames), but also forany other frames that happen to share the link (e.g., the F frames).During this blocking event, the link 106 is completely unused, whichseriously degrades the measurements of network efficiency.

FIG. 2 shows a simplified example of how virtual channels may minimizethe effects of blocking In FIG. 2, the physical link 106 is treated astwo logical (i.e., “virtual”) links The single queue 108 is replaced bytwo queues 112, 114, and the single buffer is replaced by two buffers116, 118. The frames placed into queue 112 traverse link 106 to reachbuffer 116, while the frames placed into queue 114 traverse link 106 toreach buffer 118. In normal operation, switch 102 will take turnssending frames from each queue. However, if congestion causes one of thebuffers (e.g., buffer 116) to fill, switch 102 can stop sending from onequeue (e.g., queue 112) and continue sending from the other queue (e.g.,queue 114). Thus, link 106 continues to carry frames during a blockingevent, thereby avoiding serious degradation of network efficiencymeasurements.

Today, switches and other network components (e.g. routers and hubs) usevirtual channels to not only solve network efficiency problems, but alsoto ensure quality of service (QoS). QoS is the prioritization of networkframes into groups that are given certain network characteristics (e.g.low latency or high bandwidth). These groups can be mapped, or assignedto virtual channels that are designed to provide the desiredcharacteristics. For example, critical network message frames may bemapped to a virtual channel that has been given a higher priority. Ifother frames are competing for the same resources as critical networkmessages, the higher-priority frames may be given precedence over thecompeting frames rather than being forced to “wait their turn”.

Of course, virtual channels will only be useful if multiple channels areused. Thus it becomes necessary to assign frames to different virtualchannels. The mapping of frames to a virtual channel may be carried outby logic embedded in the switch. This logic may create a correspondencebetween certain frame characteristics and virtual channels. Each framepossessing the necessary characteristics may get mapped to a particularvirtual channel.

Fibre Channel (FC) networks employ the virtual channel concept. A singleFC link can carry data at rates exceeding 2 gigabits per second (Gb/s)in both directions simultaneously. Each link can use numerous virtualchannels to prevent blocking and to ensure high throughput. The FCprotocol provides a standardized frame structure for transporting thedata.

Due to the increased importance and availability of virtual channelenabled networking devices, numerous compatibility issues have arisenstemming from the fact that devices with differing numbers of virtualchannels cannot be easily connected. For example, some devices may use16 or more virtual channels on a single physical link, while others mayonly use two virtual channels per physical link. In addition, even whenthe number of virtual channels is identical, some devices may usedifferent virtual channel mapping protocols. In this case, identicalframes may be mapped to different virtual channels across the devices,creating an incompatibility when the devices are directly linked. Itwould be desirable to eliminate these compatibility issues, therebypermitting networking devices to be interconnected with models that havedifferent virtual channel characteristics.

SUMMARY

Virtual channel enabled networking devices may map frames to specificvirtual channels based upon frame characteristics (e.g. destinationaddress, class of service). Devices and methods that provide a remappingof virtual channels are disclosed. In one embodiment, a network havingvirtual channel remapping may include: a first set of one or moreswitches that each support a first number of virtual channels, and asecond set of one or more switches that each support a second number ofvirtual channels different from the first number of virtual channels. Atleast one switch from the second set is coupled to at least one switchfrom the first set and is configured to establish a correspondence(“map”) between the virtual channels supported by the first set and thevirtual channels supported by the second set.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the disclosed method can be obtained when thebackground and following detailed description of the preferredembodiment is considered in conjunction with the following drawings, inwhich:

FIG. 1 shows an exemplary network without virtual channels;

FIG. 2 shows an exemplary network configured with virtual channels;

FIG. 3 shows a Fibre Channel frame format according to Fibre Channelstandards;

FIG. 4 shows a switch in accordance with preferred embodiments; and

FIGS. 5 and 6 show the layout of a remapping table in accordance withvarious embodiments of the invention.

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and will herein be described in detail. Itshould be understood, however, that the drawings and detaileddescription thereto are not intended to limit the invention to theparticular form disclosed, but on the contrary, the intention is tocover all modifications, equivalents and alternatives falling within thespirit and scope of the present invention as defined by the appendedclaims.

NOTATION AND NOMENCLATURE

Certain terms are used throughout the following description and claimsto refer to particular components and systems. It is recognized thatcompanies may refer to components by different names. This document doesnot intend to distinguish between components and systems that differ inname but not function. In the following discussion and in the claims,the terms “including” and “comprising” are used in an open-endedfashion, and thus should be interpreted to mean “including, but notlimited to . . . ”. Also, the term “couple” or “couples” is intended tomean either an indirect or direct electrical connection. Thus, if afirst device couples to a second device, that connection may be througha direct electrical connection, or through an indirect electricalconnection via other devices and connections.

DETAILED DESCRIPTION

FIG. 3 shows the layout of a typical Fibre Channel (FC) frame accordingto the Fibre Channel Frame and Signaling (FC-FS) specification. Itincludes the following six fields: start of frame 40, fixed header 42,variable header 44, payload 46, cyclic redundancy check 48 (CRC), andend of frame 50. The start of frame 40 is a sequence of four bytes usedto achieve synchronization between switches. When a switch receivesinformation from the transmitting switch, the receiving switch utilizesthe start of frame field to identify the information that follows as aFC frame. The start of frame 40 also indicates the class of service theframe is utilizing.

Four classes of service may be available: Class 1, Class 2, Class 3, andClass F. Class 1 service may be used for information transfers needingdedicated, uninterrupted connections. Class 2 service may be used fortransfers requiring an acknowledgement (ACK) of successful delivery offrames. Class 3 service may be used for transfers not requiring deliveryverification. Lastly, class F service may be used for inter-switchcommunications.

Both Class 1 and 2 services support a one source to one destination, or“one-to-one” transfer mode called unicasting. Class 3 service may beused for transfers to many destinations, i.e., a “one-to-many” transfermode called multicasting.

Referring still to FIG. 3, the next field in a FC frame is the fixedheader 42. The fixed header 42 is a sequence of 24 bytes comprising adestination address field 52 (D_ID), a class specific control field 56(CS_CTL), and a source address field 54 (S_ID). The destination addressfield 52 identifies the intended receiver of the frame, while the sourceaddress field 54 identifies the creator of the frame. The destinationand source address fields may be used to determine the route a frame maytake through the network. For example, when a switch receives a frame,it may use the destination address field 52 to determine the outgoingswitch port for the frame.

The control field 56 in the fixed header may be used to send controloptions with a frame. The options may be specific to a frame's class ofservice. For example, a class 1 frame may request an acknowledgementfrom the destination switch by setting the corresponding option in thecontrol field 56.

The variable header 44 and the payload 46 share an allocated space in aFC frame. The variable header 44 is an optional part of the FC framestandard that is used for particular frame types. It may vary in size upto 64 bytes to provide additional header fields as needed.

The payload 46 of the frame contains the information that is beingcarried in the frame. It may grow as large as 2,112 bytes if no variableheader is included.

The Cyclic Redundancy Check (CRC) field 48 in a FC frame is a four byteerror-detecting feature of the frame structure. If a frame becomescorrupted during transmission, the CRC field 48 may be used to determineif the frame needs to be retransmitted.

Finally, the end of frame field 50 is a sequence of four bytes. As thename suggests, this field is used to terminate a frame complying withthe FC standard.

In order to control the flow of FC frames in a FC network, a switch orother networking device uses a credit flow control mechanism. Thismechanism ensures that the buffers on a switch or other networkingdevice do not get overrun with information. When a switch is ready toreceive a frame, the switch issues a credit to the sender. The creditsare used by the sender to track the number of additional frames that maybe sent to the switch issuing the credit. The credit may come in twoforms: end-to-end (EE) and buffer-to-buffer (BB).

EE credit may be used for class 1 and 2 levels of service. EE credit mayindicate the number of frames that can be sent to a receiver switchwithout receiving an acknowledgement. Each time a device sends a frame,it decrements the EE credit associated with the destination of thatframe. Each time the device receives an acknowledgment (ACK) frame fromthat destination, the device increments the EE credit associated withthat destination. If the EE credit reaches zero and no acknowledgementis received, there may have been a buffer overrun or a transmissionerror. The sending switch may then try to negotiate another connectionand retransmit the information.

BB credit may be used for class 2 and 3 levels of service. BB creditindicates the number of frames that can be received by a receivingdevice before that device's receive buffers become full. Each time adevice sends a frame, the BB credit associated with the destination ofthat frame may be decremented. Each time a device receives a ready (RDY)frame from that destination, the device increments the BB creditassociated with that destination. If the BB credit reaches zero and noready frame is received, there may have been a buffer overrun. Thesending switch may then try to renegotiate the credit and retransmit theinformation.

Virtual channels may be used to increase the network's efficiency oftransporting frames. As described previously with respect to FIG. 2, aphysical link may be associated with multiple logical (“virtual”)channels. Each frame that traverses a link may be associated with one ofthe virtual channels, and may accordingly be routed to a receive bufferassociated with that virtual channel. (In actuality, a single receivebuffer may be used, but understanding of the virtual channel concept maybe aided by assuming that each virtual channel has a correspondingreceive buffer.)

The sender of each frame may initially determine which virtual channelthat the frame uses based on several considerations. In one networkembodiment, the virtual channel selection may be based on framecharacteristics such as the class of service and the destinationaddress. As just one example, the virtual channels may be prioritized,with the highest-numbered virtual channel having priority over thelower-numbered virtual channels. In such an example, the Class F framesused for inter-switch communications may be assigned to the virtualchannel having the highest priority due to the essential nature of suchcommunications within the FC network. It is generally expected thatresponse frames (e.g., frames that carry acknowledgement (ACK) messagesand credit messages) will be sent on the same virtual channel as thatassociated with the triggering frames, though may not be required in allembodiments.

Any one of numerous methods may be employed to inform the receiver of aframe about the virtual channel associated with that frame. For example,a field may be included in the fixed header to indicate a virtualchannel identifier. Alternatively, a time-division multiplexing schememay be employed that automatically associates each frame with a virtualchannel. Other methods are also contemplated and may be employed.

The foregoing description carries with it an underlying assumption thateach of the switches in the network will support the same number ofvirtual channels. In networks having switches made by differentmanufacturers or even different generations of switches from a givenmanufacturer, this assumption may not hold true. In preferred networkand switch embodiments, a virtual channel remapping functionality isprovided to overcome any such virtual channel discrepancy.

A switch configured with this virtual channel remapping functionalitymay first determine the virtual channel mapping protocols of the othernetwork devices to which it is connected. Using these virtual channelmapping protocols, the switch configured with the virtual channelremapping functionality is able to remap frames between differentvirtual channel mapping protocols, and is further able to carry outacknowledgement and credit transactions on the appropriate virtualchannels. More specifically, when a switch receives a frame mapped inaccordance with a first mapping protocol, the switch is able to remapthe frame's virtual channel assignment in accordance with a secondprotocol, and is able to remap response frames from the second protocolback to the first protocol.

When a link is first established between two switches, both switchescarry out an initialization or handshaking procedure. As part of thisprocedure, information identifying the manufacturer, model, and othercharacteristics of each switch may be exchanged. The informationexchange may include some direct or indirect (e.g., the manufacturername) indication of the number of virtual channels supported by eachswitch and the mapping protocol employed by each switch. In someembodiments, a switch having the virtual channel remapping functionalitymay determine that it is necessary to deceive the other switch in orderto establish communications. For example, if an older switch refuses tocommunicate with a newer switch that supports a greater number ofvirtual channels, the newer switch may unilaterally re-initiate theconnection and try to establish communications by claiming a virtualchannel capability that is compatible with the older switch.

FIG. 4 illustrates switch 402 with remapping functionally in accordancewith preferred embodiments. Switch 402 may comprise N ports, numbered406, 408, 410, and 412. Each port may further be configured with anumber of virtual channels. Switch 402 may also comprise routing logic404 that is responsible for receiving incoming frames and utilizing arouting table to determine which port the frame may exit switch 402upon. The port determined by routing logic 402 that a particular frameexits switch 404 on is herein referred to as the “exit port”.Correspondingly, the port a frame enters switch 404 on is hereinreferred to as the “entry” port.

Each port in switch 402 may further comprise remapping logic (notexplicitly shown) to carry out remapping functionality. This remappinglogic may be responsible for determining the virtual channel protocol ofthe switch connected to the port. In addition, the remapping logicassociated with each port may remap incoming and outgoing frames toensure compatibility between the switches. For example, switch 402 withremapping functionality may accept an incoming frame from a connectedswitch that utilizes a particular protocol. The entry port for thisframe may be Port 406. After reception of this frame, remapping logic inPort 406 may remap the frame to any protocol supported by the switch 402with remapping functionality.

By default, the remapping logic may remap virtual channels to theprotocol having the largest number of virtual channels supported byswitch 402. Routing logic 404 then may examine frame characteristics todetermine the exit port of the frame. For exemplary purposes, assume theexit port of a frame is Port 408. Once this exit port has beendetermined, the frame may be switched to the determined exit port. Whileat the exit port, in this case Port 408, the frame may be remapped bythe remapping logic associated with Port 408 in accordance with protocolutilized by the device connected to Port 408. The protocol utilized bythe device connected to Port 408 has preferably been stored in theremapping logic associated with Port 408 during an initializationprocedure. This protocol comprises, at the minimum, the numbers ofvirtual channels utilized by the connected device.

In alternative embodiments, the switch with remapping functionality maychange the default VC mapping protocol employed at its ports inaccordance with connected switches. For example, if the device connectedto the entry port of a switch with remapping functionality utilizes thesame mapping protocol as the device connected to the exit port, theswitch with remapping functionality may utilize this protocol for itsown ports. Therefore, the frame may be sent through the switch withremapping functionality without any necessary remapping. For example,assume a switch that supports eight virtual channel is connected to Port406 and a switch connected to Port 412 also utilizes eight virtualchannels. When a frame enters switch 402 on Port 406 and exits on Port412, only eight virtual channels may be employed on switch 402. Insteadof utilizing all 16 virtual channels associated with switch 402, theremapping logic associated with both ports may request to utilize only 8virtual channels. Therefore, no remapping is be required. The frame mayexit switch 402 on the same virtual channel as it entered on.

FIG. 5 illustrates a first exemplary remapping table that is coupled tothe remapping logic associated with each port in a switch with remappingfunctionality. This table may reside in a register, non-volatile memory,or other port accessible storage mechanism. This first remapping tableis used to remap incoming transfers for a switch with remappingfunctionality that supports 16 virtual channels. The table comprisessixteen entries, one for each virtual channel. In addition, four bitsare reserved for each virtual channel to store the remapped virtualchannel number. For example, if the value <0100> (binary equivalent to4) is written to bits <35:32> all incoming frames arriving on virtualchannel 8 are remapped to virtual channel 4 of the switch with remappingfunctionality.

FIG. 6 illustrates a second exemplary remapping table that is coupled tothe remapping logic associated with each port in a switch with remappingfunctionality. This table may reside in a register, non-volatile memory,or other port accessible storage mechanism. This second remapping tableis used to remap outgoing transfers for a switch with remappingfunctionality that supports 16 virtual channels. The table comprisessixteen entries, one for each virtual channel. In addition, four bitsare reserved for each virtual channel to store the remapped virtualchannel number. For example, if the value <0011> (binary equivalent to3) is written to bits <35:32> all outgoing frames leaving on virtualchannel 8 of the switch with remapping functionality are remapped tovirtual cannel 3 of the connected switch.

When a switch is connected to the switch with remapping functionality,the virtual channel mapping protocol is identified to the remappinglogic associated with the port through the switch initializationprocedure. The remapping logic utilizes this virtual channel protocol towrite the proper information into the incoming and outgoing remappingtables in FIGS. 5 and 6. For example, consider the case when a firstswitch that supports eight virtual channels is connected to a secondswitch with remapping functionality that supports 16 virtual channels.Each frame may be mapped to a virtual channel by the first switchutilizing three bits. These three bits may place the frame into one ofeight virtual channels. When the second switch receives the frame, itmust utilize an additional bit to remap the frame into one of the 16virtual channels. This additional bit preferably is identifiedautomatically by the remapping logic associated with the port on thesecond switch based upon the virtual channel protocol received duringthe initialization procedure. Usually the most significant bit (MSB) orthe least significant bit (LSB) of the destination address contained inthe frame header is utilized. In alternative embodiments, the networkadministrator may manually configure the remapping logic to utilizedefined bit(s) for remapping.

Once the first and second remapping tables preferably are written by theremapping logic, all frames that enter and exit the switch withremapping functionality may be remapped accordingly. Frames entering theswitch with remapping functionality are remapped by remapping logicassociated with the port they arrived on. This remapping logic utilizesthe first remapping table in FIG. 5. In addition, credits and otheroutgoing transfers are remapped by remapping logic associated with theport they are being sent out on. This remapping logic utilizes thesecond remapping table in FIG. 6. Hence, the remapping tables areutilized for all incoming and outgoing transfers on the switch withremapping functionality.

The aggregate number of remapping tables associated with a switchconfigured with remapping functionality is determined by the number ofports utilized by the switch. For example, in a 16-port switch, eachport will have one output remapping table, as shown in FIG. 6, and oneinput remapping table, as shown in FIG. 5. Thus, a total of 16 inputremapping tables and 16 output remapping tables exist in the switch.Alternatively, specific ports may be configured with remappingfunctionality. Each port preferably possesses an output and inputremapping register coupled to the remapping logic associated with theport.

In alternative embodiments, the remapping table in FIG. 5 and FIG. 6 maybe manually written by a network administrator. This ensures that allpossible virtual channel remapping combinations may be achieved. Forexample, a network administrator may desire to assign the high priorityvirtual channel (i.e. virtual channel 0) of a connected switch to thehigh priority virtual channel of the switch with remappingfunctionality. The remapping logic may not automatically create thisremapping due to the bit that is utilizing to remap the virtualchannels.

Although a Fibre Channel (FC) network was used in the preferredembodiment, the disclosed method may be equivalently implemented onnumerous other types of network architectures. FIG. 7 shows a computersystem 700 coupled to a storage device 702 by a network 704. Thecomputer system 700 may be any suitable node device including a desktopcomputer, a server, or a user terminal. Storage device 702 may similarlybe any suitable node device including a hard drive, RAID array, ornetwork data store. Network 704 is shown having six switches 706, 708,710, 712, 714, and 716 coupled together via inter-switch links (ISLs).The switches may have as few as four and as many as 256 or more ports.Some possible types of networks that may utilize the disclosed methodare discussed below.

Synchronous Optical networks may employ a switch topology for opticalcommunications. More information regarding Synchronous Optical standardsmay be found at www.iec.org/online/tutorials/sonet.

The disclosed methods may equally be implemented on token-passingnetworks. These networks move a small frame, called a token, around thenetwork. Possession of the token may grant the right to transmit. If anode receiving the token has no information to send, it may pass thetoken to the next node of the network. Two types of token networks areToken Ring networks standardized in IEEE 802.5 and Fibre DistributedData Interface (FDDI) networks, developed by the American NationalStandards Institute (ANSI) X3T9.5 standards committee.

Finally, Ethernet network standards may be found in IEEE 802.3,illustrating a commonly used switch-based topology again suitable forimplementation of the disclosed method. Ethernet may be a local areanetwork technology that transmits information between computers atspeeds of 10 and 100 million bits per second (Mbps). Both versions ofEthernet technology may employ a similar switch based topology suitablefor implementation of the disclosed invention.

Numerous variations and modifications will become apparent to thoseskilled in the art once the above disclosure is fully appreciated. It isintended that the following claims be interpreted to embrace all suchvariations and modifications.

1.-54. (canceled)
 55. A device that comprises: a port that receives dataon a first number of virtual channels and sends the data on a secondnumber of virtual channels; wherein the first number is not equal to thesecond number.
 56. The device of claim 55, further comprising a secondport that receives the data on the second number of virtual channels.57. The device of claim 55, further comprising a second port that sendsthe data on a third number of virtual channels, wherein the third numberis not equal to the second number.
 58. The device of claim 55, whereinacknowledgement data and credit transaction data are returned on thefirst number of virtual channels.
 59. The device of claim 55, whereinthe second number of virtual channels comprises a different number ofvirtual channels dedicated to a class than the first number of virtualchannels dedicates to the class.
 60. The device of claim 55, wherein theport determines the first number of virtual channels duringinitialization.
 61. The device of claim 55, wherein, if aninitialization attempt fails because the port represents that the portsupports a fourth number of virtual channels, the port represents thatit supports the first number of virtual channels during anotherinitialization attempt, the first number not equal to the fourth number.62. The device of claim 55, wherein the second number is the maximumnumber of virtual channels supported by the device.
 63. The device ofclaim 55, further comprising routing logic that internally routs thedata on the second number of virtual channels.
 64. The device of claim55, further comprising a second port that receives the data on thesecond number of virtual channels and sends the data on a third numberof virtual channels, wherein the third number is not equal to the secondnumber.
 65. The device of claim 55, further comprising remapping logicthat determines the virtual channel protocol of the first number ofvirtual channels.
 66. A method comprising: receiving data on a firstnumber of virtual channels; sending the data on a second number ofvirtual channels, the first number not equal to the second number. 67.The method of claim 66, further comprising remapping the first number ofvirtual channels into a third number of virtual channels, and remappingthe third number of virtual channels into the second number of virtualchannels.
 68. The method of claim 66, further comprising internallyrouting the data on a third number of virtual channels, the third numbernot equal to the first number.
 69. The method of claim 66, furthercomprising returning acknowledgement data and credit transaction data onthe first number of virtual channels.
 70. The method of claim 66,further comprising dedicating to a class a different number of virtualchannels out of the second number of virtual channels than dedicated tothe class out of the first number of virtual channels.
 71. The method ofclaim 66, further comprising determining the first number of virtualchannels during initialization.
 72. The method of claim 66, furthercomprising reattempting initialization representing support of the firstnumber of virtual channels if a prior initialization attempt failedwhile representing support of a fourth number of virtual channels, thefirst number not equal to the fourth number.
 73. The method of claim 66,further comprising remapping the first number of virtual channels intothe second number of virtual channels; and remapping the second numberof virtual channels into the first number of virtual channels.
 74. Themethod of claim 66, further comprising determining the virtual channelprotocol of the first number of virtual channels.